Systems and methods for performing replication copy storage operations

ABSTRACT

A system and method are provided for performing storage operations relating to a first secondary copy of electronic data. A storage policy or storage preferences may dictate that a replication copy should be used in storage operations performed to a particular client, sub-client, data, media or other item. Based on the storage policy, when a new client, sub-client, data, media or other item is received, a media agent determines whether there is a replication copy of the item. In the absence of a replication copy, one may be created. Information regarding the replication copy and its corresponding first secondary copy may be stored in a database. To optimize use of system resources, storage operations relating to the first secondary copy may be performed using the replication copy instead of the first secondary copy.

RELATED APPLICATION

This application is a continuation of U.S. patent Ser. No. 12/581,297,filed Oct. 19, 2009, which is a continuation of U.S. patent applicationSer. No. 11/313,257, filed Dec. 19, 2005, each of which is herebyincorporated herein by reference in its entirety to be considered partof this specification.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosures, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise expressly reserves allother rights to copyright protection.

BACKGROUND

1. Field of the Invention

The invention disclosed herein relates generally to performing storageoperations on electronic data in a computer network. More particularly,the present invention relates to using a replication copy or other copyof primary storage production data for performing storage operations.

2. Description of the Related Art

Current storage management systems employ a number of different methodsto perform storage operations on electronic data. For example, data canbe stored in primary storage as a primary copy or in secondary storageas various types of secondary copies including, a backup copy, asnapshot copy, a hierarchical storage management copy (“HSM”), as anarchive copy, and as other types of copies.

A primary copy of data is generally a production copy or other “live”version of the data which is used by a software application and isgenerally in the native format of that application. Primary copy datamay be maintained in a local memory or other high-speed storage devicethat allows for relatively fast data access if necessary. Such primarycopy data is typically intended for short term retention (e.g., severalhours or days) before some or all of the data is stored as one or moresecondary copies, for example to prevent loss of data in the event thata problem occurred with the data stored in primary storage.

Secondary copies include point-in-time data and are typically intendedfor long-term retention (e.g., weeks, months or years depending onretention criteria, for example, as specified in a storage policy asfurther described herein) before some or all of the data is moved toother storage or discarded. Secondary copies may be indexed so thatusers can browse and restore the data at another point in time. Aftercertain primary copy data is migrated to secondary storage, a pointer orother location indicia such as a stub may be placed in the primary copyto indicate the current location of that data.

In conventional storage management systems, a secondary copy istypically produced by performing a storage operation, such as a backup,of production data, such as a primary copy. Creating such secondarycopies typically requires taking the production data or primary copyoffline so that it is inaccessible or unavailable to a client or othersystem component. In general, it is preferable to avoid taking a primarycopy, and any components associated therewith, offline, however, if itis unavoidable, it is preferable to minimize the duration that thecopies or components are offline. Storage operations that require theprimary copy are typically scheduled overnight when the primary copy isless likely to be used by a client, which typically accesses the primarycopy during daytime hours. Thus, the primary copy may often beunavailable, or access to the primary copy may be difficult to providebecause it is frequently in use. In addition storage management systemcomponents using the primary copy for storage operations may also beunavailable to perform other concurrent storage operations. Such systemsmay encounter bottlenecks in allocation of system resources to performstorage operations.

SUMMARY

Systems and methods are provided for performing a storage operationusing a replication copy or other data source. In one embodiment, amethod for performing a storage operation using a replication copy isprovided in which a data item for a storage operation is identified, astorage policy associated with the data item is identified, and a datasource of the data item may be determined to be available. The datasource for performing the storage operation may be selected according toa criterion and the storage operation may be performed. The data sourcemay be a first secondary copy or a replication copy. In general, thedata source is determined by consulting a schedule of storage operationsinvolving the data source. A storage manager or other system componentmay select the data source according to a criterion by calculating ametric weighing one or more priorities for storage operationpreferences.

In another embodiment, a method for performing a storage operation usinga replication copy is provided, in which a storage operation instructionis received. The storage operation instruction may include dataidentifying a data item with which to perform the storage operation. Astorage policy may be received. The storage policy may indicate that astorage operation relating to the data item should be performed using areplication copy. The replication copy may be determined to be availableand the storage operation may be performed using the replication copy.

In another embodiment, a method for optimizing storage operations in astorage management system is provided, in which, a storage operationrequest is received, the storage operation request identifying a dataitem with which to perform the storage operation. A database may beconsulted to determine whether a replication copy of the data item isavailable. Using the replication copy of the data item to perform thestorage operation may be determined to optimize resource use in thestorage management system; and the storage operation may be performedusing the replication copy.

In another embodiment, a storage management system for performing astorage operation, is provided including a storage management componentcommunicatively coupled to a database; wherein the database includes astorage policy; a media agent communicatively coupled to the storagemanagement component, a first secondary copy and a replication copy;wherein the storage management component is programmed to receive astorage operation request relating to the first secondary copy, consultthe database to identify the replication copy that corresponds to thefirst secondary copy, and determine whether using the replication copyto perform the storage operation optimizes use of system resources; andwherein the media agent is programmed to perform the storage operationusing the replication copy.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention is illustrated in the figures of the accompanying drawingswhich are meant to be exemplary and not limiting, in which likereferences are intended to refer to like or corresponding parts, and inwhich:

FIG. 1A is a block diagram of a storage management system for creating areplication copy according to an embodiment of the invention;

FIG. 1B is a diagram of a log and a file according to an embodiment ofthe invention;

FIG. 2 is a block diagram of a storage management system according to anembodiment of the invention;

FIG. 3 is a high level block diagram of a storage management systemaccording to an embodiment of the invention;

FIG. 4 is a storage operation schedule according to an embodiment of theinvention;

FIG. 5 is a database table for tracking copy volumes according to anembodiment of the invention; and

FIG. 6 is a flow diagram of a method for performing a storage operationaccording to an embodiment of the invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Systems and methods are provided herein for performing a storageoperation using a replication copy. A replication copy may be a copy ofa first secondary copy of production data (e.g., a primary volume), butmay also be a copy of production data or a primary copy. A firstsecondary copy is an initial or first secondary copy of production data,or some other initial copy of the primary volume. The first secondarycopy may be considered for data storage management purposes to includethe same data as a primary copy. The first secondary copy may be storedto primary storage, which is a storage medium which provides relativelyfaster access than secondary storage, however, secondary storage mediummay also be used for the first secondary copy. The first secondary copymay alternatively refer to any copy of electronic data which may befrequently accessed by one or more system components for client use orstorage operation purposes, and for which utilization may need to berestricted, e.g., to avoid bottlenecks, to avoid interrupting client useetc. In this case, the first secondary copy may be considered equivalentto a primary copy in that storage management systems may wish tominimize system utilization of the first secondary copy as it would fora primary copy.

There are several ways to create a replication copy, such as byperforming a copy operation, such as a snapshot copy, point in timecopy, mirror copy, synchronous replication copy or asynchronousreplication copy, or other copy operation. A replication copy istypically made of a first secondary copy and continuously updated. Oneexample of a system for creating a replication copy is shown in FIG. 1A,but other system architectures may be used. As shown in FIG. 1A, asystem for creating a replication copy may include system componentssuch as a memory or data store 10, log filter driver 20, primary massstorage 40, logs 30, replication agent 87 and storage manager 100 andstorage management index or database 111 and a replication copy 200.

In general, a replication copy 200 may be created at the direction of areplication agent 87, storage manager 100 or other system component, andinformation relating to the replication copy 200 may be stored in anindex 111. The replication agent 87 may obtain the electronic data, suchas from production data or a first secondary copy stored in memory 10,for the replication copy continuously via one or more data streams, oruse logs 30 which include a production data log or change informationobtained by the log filter driver 20, to update a replication copyperiodically. The replication agent 87 may communicate with the logfilter driver 20 to acknowledge receipt of logs 31 from a logs store orcache 30 or directly from the logs filter driver 20, and confirm thatthe replication copy 200 is updated with the received logs 31.

Memory 10 may be a data store which is attached to a client or otherdata generator or data producer and which is capable of storingelectronic data, such as production data or a first secondary copy, etc.A log filter driver 20 may be a module which monitors an interaction orchange of electronic data in memory 10. The log filter driver 20 may beprogrammed to monitor particular or specific data changes, such aschanges to a sub-client, application type, client folder, or otheraspect of electronic data. Referring to FIG. 1B, the interaction orchange may be stored in a log 31 which includes metadata, such as a fileID 32 and offset 34 and the changed data payload 36. A file ID 32 may beany file identifier and may correspond to a file 35. The offset 34 isthe point at which the change to the file data occurs. Payload 36typically includes the changed data. Thus, the file log 31 relates tothe file 35 in that the payload 36 of the log 31 fits in the file 35 ata certain offset point, for example, between portions of the file 38Aand 38B.

Referring again to FIG. 1A, the log filter driver 20 monitors theproduction data stored in memory 10 for interactions or changes to theelectronic data and when a change occurs, the log filter driver 20creates a log, such as log 31, which is stored in logs 30. A log file 31may be cached temporarily in logs 30 or transmitted immediately to thereplication copy 200 for updating the replication copy 200. Logs 30 maybe any data store capable of storing the logs 31 generated by the logfilter driver 20, and is generally in communication with a replicationagent 87, replication copy 200, or other system component. The logfilter driver 20 may also create logs 31 which may be used to create aprimary copy or first secondary copy, stored in mass storage 40. Themass storage 40 may be any data store capable of storing electronicdata, such as a primary copy, first secondary copy or other copy.

FIG. 2 illustrates a block diagram of a storage operation cell 80 thatmay perform storage operations on electronic data in a computer networkin accordance with an embodiment of the present invention. As shown,storage operation cell 80 may generally include a storage manager 100, adata agent 95, a media agent 105, a storage device 115, and, in someembodiments, may include certain other components such as a client 85, areplication agent 87, a data or information store 90, databases orindexes 110 and 111, jobs agent 120, an interface module 125, and amanagement agent 130. Such system and elements thereof are exemplary ofa modular storage management system such as the CommVault QINETIXsystem, and the CommVault GALAXY storage management system, availablefrom CommVault Systems, Inc. of Oceanport, N.J., and further describedin U.S. patent application Ser. No. 09/610,738 which is incorporatedherein by reference in its entirety. A storage operation cell, such ascell 80, may generally include combinations of hardware and softwarecomponents associated with performing storage operations on electronicdata.

In accordance with certain embodiments of the present invention, storageoperations performed by storage operation cells may include creating,storing, retrieving, and migrating primary data copies and secondarydata copies (which may include, for example, snapshot copies, backupcopies, HSM copies, archive copies, and other types of copies ofelectronic data). In some embodiments, storage operation cells may alsoprovide one or more integrated management consoles, for users or systemprocesses to interface with in order to perform certain storageoperations on electronic data as further described herein. Suchintegrated management consoles may be displayed at a central controlfacility or several similar consoles distributed throughout multiplenetwork locations to provide global or geographically specific networkdata storage information.

In some embodiments, storage operations may be performed according to astorage policy. A storage policy is generally a data structure or otherinformation source that includes a set of preferences and other storagecriteria for performing a storage operation. The preferences and storagecriteria may include, but are not limited to, a storage location,relationships between system components, relationships between systemcomponents and use of a third party application, network pathway toutilize, retention policies, data characteristics, compression orencryption requirements, preferred system components to utilize in astorage operation, and other criteria relating to a storage operation.Thus, a storage policy may indicate that certain data is to be stored ina specific storage device, retained for a specified period of timebefore being aged to another tier of secondary storage, copied tosecondary storage using a replication copy or a specified number ofstreams, etc. A storage policy may be stored to a storage managerdatabase or index 111, to archive media as metadata for use in restoreoperations or other storage operations, or to other locations orcomponents of the system.

A schedule policy may specify when and how often to perform storageoperations and may also specify performing certain storage operations onsub-clients of data and how to treat those sub-clients. A sub-client mayrepresent static or dynamic associations of portions of data of a volumeand are mutually exclusive. Thus, a portion of data may be given a labeland the association is stored as a static entity in an index, databaseor other storage location used by the system. Sub-clients may also beused as an effective administrative scheme of organizing data accordingto data type, department within the enterprise, storage preferences,etc. For example, a sub-client may be all media in an associated storagedevice and the sub-client is associated with a storage policy whichrequires that a replication copy be created or provided to performsecondary storage operations.

Storage operation cells may contain not only physical devices, but alsomay represent logical concepts, organizations, and hierarchies. Forexample, a first storage operation cell 80 may be configured to performa storage operation, such as data backup or other types of datamigration, and may include a variety of physical components including astorage manager 100 (or management agent 130), a media agent 105, aclient component 85, and other components as described herein. A secondstorage operation cell may contain the same or similar physicalcomponents, however, it may be configured to perform other storageoperations, such as monitoring a primary copy, first secondary copy, orreplication copy volume or performing other known storage operations.

A storage preference may be a storage policy, user preference or otherstorage preference. In some embodiments the storage preference isdefined by a system user or system administrator. In other embodiments,the storage preference is a default preference. Examples of storagepreferences can include: using a particular data source for performing astorage operation, such as a replication copy, assigning priorities toperformance of a storage operation, data security settings, encryptionsettings, data retention requirements, frequency of storage operations,such as frequency of backups, types of data for storage operations, suchas data types for backups, types of storage operations to perform in thecomponent group, network pathways, such as preferred network pathways toperform a storage operation, scheduling, such as a schedule of storageoperations, reports, such as automatic generation of system reportsregarding the group, which can include, for example the storageoperations performed by the group, or other storage preference.

Replication agent 87 may be a software module or part of a softwaremodule that may be used to manage and direct creation and maintenance ofa replication copy 200. For example, a replication agent 87 maycommunicate or direct communication of electronic data, such asproduction data for creating a replication copy 200. The replicationcopy 200 may be created synchronously or asynchronously, using a mirror,or other copy technique. The replication agent 87 may be a softwaremodule associated with a client 85 that generates the production dataused to create replication copy 200. Alternatively, replication agent 87may be provided by a third party software component which may interfacewith a client 85 and production data in, for example, data store 90, tocreate replication copy 200.

Data agent 95 may be a software module or part of a software module thatis generally responsible for archiving, migrating, and recovering datafrom client computer 85 stored in an information store 90, or othermemory location. Each client computer 85 may have at least one dataagent 95 and the system can support multiple client computers 85. Insome embodiments, data agents 95 may be distributed between client 85and storage manager 100 (and any other intermediate components (notshown)) or may be deployed from a remote location or its functionsapproximated by a remote process that performs some or all of thefunctions of data agent 95.

Embodiments of the present invention may employ multiple data agents 95each of which may backup, migrate, and recover data associated with adifferent application. For example, different individual data agents 95may be designed to handle MICROSOFT EXCHANGE data, LOTUS NOTES data,MICROSOFT WINDOWS 2000 file system data, MICROSOFT ACTIVE DIRECTORYOBJECTS data, and other types of data known in the art. Otherembodiments may employ one or more generic data agents 95 that canhandle and process multiple data types rather than using the specializeddata agents described above.

Generally speaking, storage manager 100 may be a software module orother application that coordinates and controls storage operationsperformed by storage operation cell 80. Storage manager 100 maycommunicate with some or all elements of storage operation cell 80including client computers 85, data agents 95, media agents 105, andstorage devices 115, to initiate and manage system storage operations.

Storage manager 100 may include a jobs agent 120 that monitors thestatus of some or all storage operations previously performed, currentlybeing performed, or scheduled to be performed by storage operation cell80. Jobs agent 120 may be communicatively coupled with an interfaceagent 125 (typically a software module or application). Interface agent125 may include information processing and display software, such as agraphical user interface (“GUI”), an application program interface(“API”), or other interactive interface through which users and systemprocesses can retrieve information about the status of storageoperations. Through interface 125, users may optionally issueinstructions to various storage operation cells 80 regarding performanceof the storage operations as described and contemplated by the presentinvention. For example, a user may modify a schedule concerning thenumber of pending snapshot copies or other types of copies scheduled asneeded to suit particular needs or requirements. As another example, auser may employ the GUI to view the status of pending storage operationsin some or all of the storage operation cells in a given network or tomonitor the status of certain components in a particular storageoperation cell (e.g., the amount of storage capacity left in aparticular storage device). As a further example, interface 125 maydisplay the cost metrics associated with a particular type of datastorage and may allow a user to determine overall and target costmetrics associated with a particular data type, or certain storageoperation cell 80 or other storage operation as predefined oruser-defined.

Storage manager 100 may also include a management agent 130 that istypically implemented as a software module or application program. Ingeneral, management agent 130 provides an interface that allows variousmanagement components 100 in other storage operation cells 80 tocommunicate with one another. For example, assume a certain networkconfiguration includes multiple cells 80 adjacent to one another orotherwise logically related in a WAN or LAN configuration (not shown).With this arrangement, each cell 80 may be connected to the otherthrough each respective interface module 125. This allows each cell 80to send and receive certain pertinent information from other cells 80including status information, routing information, information regardingcapacity and utilization, etc. These communication paths may also beused to convey information and instructions regarding storageoperations.

Storage manager 100 may also maintain an index cache, a database, orother data structure 111. The data stored in database 111 may be used toindicate logical associations between components of the system, userpreferences, management tasks, some SRM or HSM data or other usefuldata. As further described herein, some of this information may bestored in a media agent database 110 or other local data store accordingto some embodiments. For example, the storage manager 110 may use datafrom database 111 to track logical associations of primary copies ofdata, first secondary copies of data and corresponding replicationcopies, between media agents 105 and storage devices 115 or betweenother components of the system.

Generally speaking, a media agent 105 may be implemented as a softwaremodule that conveys data, as directed by a storage manager 100, betweena client computer 85 and one or more storage devices 115 such as a tapelibrary, a magnetic media storage device, an optical media storagedevice, or any other suitable storage device. In one embodiment, mediaagents 105 may be communicatively coupled with and control a storagedevice 115 associated with that particular media agent. A media agent105 may be considered to be associated with a particular storage device115 if that media agent 105 is capable of routing and storing data to aparticular storage device 115.

In operation, a media agent 105 associated with a particular storagedevice 115 may instruct the storage device to use a robotic arm or otherretrieval means to load or remove a certain storage media, and tosubsequently archive, migrate, or restore data to or from that media.Media agents 105 may communicate with a storage device 115 via asuitable communications path such as a SCSI or fiber channelcommunications link. In some embodiments, the storage device 115 may becommunicatively coupled to a data agent 105 via a Storage Area Network(“SAN”).

Each media agent 105 may maintain an index cache, a database, or otherdata structure 110 which stores index data generated during backup,migration, and restore and other storage operations as described herein.For example, performing storage operations on MICROSOFT EXCHANGE datamay generate index data. Such index data provides a media agent 105 orother external device with a fast and efficient mechanism for locatingdata stored or backed up. Thus, in some embodiments, a storage managerdatabase 111 may store data associating a client 85 with a particularmedia agent 105 or storage device 115, for example, as specified in astorage policy, while media agent database 110 may indicate wherespecifically the client 85 data is stored in storage device 115, whatspecific files were stored, and other information associated withstorage of client 85 data. In some embodiments, such index data may bestored along with the data backed up in a storage device 115, with anadditional copy of the index data written to index cache 110. The datain index cache 110 is thus readily available for use in storageoperations and other activities without having to be first retrievedfrom the storage device 115.

In some embodiments, certain components may reside and execute on thesame computer. For example, in some embodiments, a client computer 85such as a data agent 95, a media agent 105, or a storage manager 100coordinates and directs local archiving, migration, and retrievalapplication functions as further described in U.S. patent applicationSer. No. 09/610,738. This client computer 85 can function independentlyor together with other similar client computers 85.

As described herein, storage operations may be performed by one or moremedia agents 105 at the direction of a storage manager 100 via thestorage manager 100 or directly in communication with a client 85.Employing multiple media agents 105 in a storage system allowsflexibility in associating one or more media agents 105 with a client85, or other component. For example, one media agent 105 may beassociated with a first client 85 and perform storage operations inregard to the associated client 85, e.g., using a primary copy of thefirst client 85, and another media agent 105 may be associated with asecond client 85 and perform storage operations in regard with thesecond client 85, e.g., using a replication copy 200 of the secondclient 85. Thus, in the event that one or more system components failsor is unavailable, another system component, e.g., a media agent 105,may be used to perform a storage operation.

Referring to FIG. 3, a replication copy 200 of a first secondary copy 90may be created by a third party application 150 or by cell componentssuch as a media agent 105 b, according to storage policies or at thedirection of a storage manager 100. First secondary copy 90 is a firstsecondary copy or other initial copy of a primary copy 86 of datagenerated by client 85. First secondary copy 90 may be created via mediaagent 105 a (which may be the same component as media agent 105 b, or aseparate component). As shown in FIG. 3, the replication copy 200 may becoupled to a media agent 105 b and hosted by host 201. Media agent 105 bor replication software on the first secondary copy 90 may be used tocreate replication copy 200, e.g., using known replication techniques.If the replication copy 200 is created by a third party application 150,the media agent 105 b may interface with the third party application 150to access the replication copy 200. The third party application 150 maybe a software module which may communicate with a media agent 105 andreplication copy 200. The media agent 105 may access the replicationcopy 200 to perform storage operations, such as creating secondarycopies stored to secondary storage 200. Although, the media agent 105may access first secondary copy 90 to perform storage operations, suchconfiguration is not ideal because first secondary copy 90 is preferablyfree for use by other system components and for other storageoperations.

One storage operation that the media agent 105 may perform in connectionwith the replication copy 200 or first secondary copy 90 is creation ofa secondary copy or other backup operation. The media agent 105 maycreate, in accordance with a storage policy, a secondary copy 220 thatmay be created using data of a replication copy 200 or first secondarycopy 90. In general, a secondary copy 220, such as an auxiliary copy,backup copy, or other copy, is stored to media that is slower than mediaused to store a first secondary copy 90 and the secondary copy 220 maybe created to migrate electronic data to storage, such as at an offsitefacility.

A storage policy stored in an index or database 110 or 111 may initiatea secondary copy operation and the media agent 105 may determine whichcopy to use for the copy operation. For example, the media agent 105 maycheck network and cell resources, storage policies, job scheduling orother storage characteristic to determine whether the first secondarycopy 90 or replication copy 200 should be used. For example, a mediaagent 105 (or storage manager, jobs agent or other system component) mayconsult a job schedule, such as a storage operation schedule 250depicted in FIG. 4. The storage operation schedule 250 may include aschedule or timeline for storage operations performed, currently inoperation or scheduled in the future. Information about storageoperation scheduling may be obtained from a storage policy, communicatedfrom one or more system components, or provided by a system user oradministrator.

In addition, preferences as to use of a replication copy, firstsecondary copy or other source data may be established for performing astorage operation, for example, in a storage policy or other preferenceassociated with one or more cells, system components, scheduling policy,retention policy, or other preference. A user may set a preference orother criteria which may be used to select a replication copy or firstsecondary copy to perform a storage operation, or alternatively, adefault template setting in a storage policy or other selectioncriteria, or a user preference may be that new media added to a storagedevice should use a replication copy in performing a storage operation,or a particular cell may include a client for which a replication copymay be used to perform storage operations, or other storage preferenceor selection criteria.

As shown, a first storage operation 252 may be scheduled to occur fromT.sub.0 to T.sub.2. The first storage operation 252 may be any storageoperation and may be associated with a storage policy, storagepreference or other criteria which may indicate a preference for usingor selecting a first secondary copy or a replication copy to perform thestorage operation. During the time period T.sub.0 and T.sub.2, a secondstorage operation 254 is scheduled to occur from T.sub.1 to T.sub.4. Thesecond storage operation 254 may also be associated with a storagepolicy or storage preference regarding a copy to use to perform thestorage operation. Overlapping with the second storage operation 254, athird storage operation 256 is scheduled for T.sub.3 to T.sub.5. As withthe first and second storage operations 252 and 254, respectively, thethird storage operation 256 may be associated with one or more storagepreferences or a storage policy. Such storage preferences may alsoinclude a relative priority weighting for performing the storageoperation, and a priority weighting for using a particular copy forperforming the storage operation, such as the first secondary copy orreplication copy. Weighting each storage preference provides the abilityto calculate an overall metric for selection of one or more aspects ofperforming the storage operation.

A storage manager, jobs agent, media agent or other system component,may consult the storage operation schedule 250 and/or an index toidentify criteria for selecting a data source, or determine a priorityof or availability to use a first secondary copy or a replication copyfor a storage operation. For example, the first storage operation 252may be associated with a storage preference that indicates that a firstsecondary copy or a replication copy may be used to perform a storageoperation, and have a medium priority level. The second storageoperation 254 may be associated with a storage preference that indicatesthat a first secondary copy is preferably used to perform a storageoperation and it has a higher priority than first storage operation 252.The third storage operation 256 may be associated with a storagepreference which indicates that a first secondary copy is preferablyused to perform a storage operation and has a medium priority level. Insuch a case, the storage manager (or jobs agent, media agent or othersystem component) may automatically select a replication copy forperforming the first storage operation 252, and a first secondary copyfor performing the second storage operation 254. The storage manager maycalculate the storage operation priority, other preferences and firstsecondary copy availability and override the data source preference withrespect to the third storage operation 256 and select or allocate thereplication copy for use in performing the third storage operation 256based on selection criteria, for example, the higher priority weightingof the second storage operation 254 and the availability of the firstsecondary copy which will be in use in the second storage operation 254at the time the third storage operation 256 is to be initiated.

A media agent 105 may consult a database table in its index 110 or astorage manager index 111 to identify a replication copy 200 thatcorresponds to a first secondary copy 90. An example of such databasetable may be the table 305 depicted in FIG. 5. As shown, table 305includes information useful in performing storage operations, such asnetwork pathways for primary copies 320 and corresponding replicationcopies 310. For example, first secondary copy 325 atc:/mydocuments/files corresponds to replication copy 345 atF:/mydocuments/files. First secondary copy 330 at c:/programfiles/files,however does not have a corresponding replication copy as shown by theempty record, 350. First secondary copy 335 at c:/database/filescorresponds to g:/database/files 355. The table 305 may also includeother information about the first secondary copies 320 and replicationcopies 310 such as a system component associated with each, media type,storage type, data content, data type, or other information. Inaddition, table 305 may include links or relational pointers between aproduction data set, primary copy, first secondary copy and areplication copy.

As described herein, using a replication copy to perform a storageoperation, which may otherwise be performed using a first secondarycopy, frees up the first secondary copy, and any system components thatmay be associated with the first secondary copy, for other uses. Forexample, a first media agent may be associated with a particular clientand its respective data agent, data store or first secondary copy, and asecond media agent may be associated with the same client and areplication copy associated with the client. In this case, the firstsecondary copy may be used to perform storage operations or otheroperations in connection with the first media agent, data agent orclient, and concurrently, the replication copy could be used by thesecond media agent to perform a secondary copy operation or otherstorage operation.

A media agent or other system component may update a table regardingreplication copy information, such as the table depicted in FIG. 5, anddirect a storage operation according to the flow diagram depicted inFIG. 6. The table provides a convenient reference point for cellcomponents to identify a replication copy associations or informationabout cell components. The table may be updated continuously asinformation about a replication copy becomes known to a media agent,storage manager or other cell component, such as a client.

A storage operation request may be received, such as a request to createa secondary copy or other which may include information for identifyingdata for performing a storage operation, step 410. The storage operationrequest may be user initiated or automatically initiated in accordancewith a storage policy, job schedule, retention policy or otherinitiator. The storage operation request may include, among otherinformation, data identifying the first secondary copy or correspondingclient having source or production data to be used in the storageoperation.

A storage policy may be identified that is associated with the data forperforming the storage operation, step 420. In general, the storagepolicy is associated in an index or data table with a data source, suchas a client, sub-client, or other system component or dataclassification. The storage policy may include one or more storagepreferences which may indicate a priority for performing a storageoperation, one or more criteria for selecting a component, data item, ordata source with which to perform a storage operation, or otherpreference. The storage policy may be user defined, a default template,or other set of preferences.

A storage manager, media agent or other system component may determinewhether a replication copy of data is available to perform a storageoperation, step 430. In general, the replication copy information may beobtained by a media agent (or other component) by consulting a table,index or database to determine whether there is a replication copy thatis associated with a first secondary copy of data targets, such as theidentified data for performing the storage operation. Generally, themedia agent will check the table for a replication copy if a storagepreference or a user preference indicates that a replication copy shouldbe used. However, even if the storage preference does not indicate thata replication copy should be used, a storage policy may have a defaultsetting such that a media agent should determine whether to use a firstsecondary copy or replication copy in accordance with optimizing systemresources, such as, for example, in accordance with availability ofsystem components and network pathways, job scheduling, or other systemcharacteristics, as described herein. Thus, a media agent may check fora replication copy whether or not a storage preference dictates use of areplication copy.

Availability of the replication copy may also include a determinationthat the replication copy is online or offline, the replication copy isin use for another storage operation, or otherwise available orunavailable. In addition to consulting the table to check foravailability, a media agent may ping or communicate with the replicationcopy to determine if it is online and available.

In the event that no replication copy exists, a media agent or storagemanager may direct the storage operation to be performed using a firstsecondary copy, step 440. Upon performance of the storage operation, theindex is updated to reflect the completed storage operation, step 455.The index may be updated to include information about the completedstorage operation, such as creation of a secondary copy, and informationabout the data source, e.g., the first secondary copy.

The media agent or storage manager may also determine whether a lack ofa replication copy of data is causing inefficiencies in performingstorage operations and may direct that in view of future storageoperations, scheduled, or anticipated, for example, based on a storagepolicy, that a replication copy be produced for all, or particular typesor data. For example, a replication copy may be created using a thirdparty application, which may be interfaced directly by a media agent, oralternatively created by the media agent, replication agent, or othersystems and methods described herein or known in the art.

If a replication copy exists, e.g., the media agent consults a table andfinds a replication copy which is associated with a first secondary copythat is the data source for the storage operation, the media agent (orother system component) may calculate a selection criteria, step 445,for selecting a data source to perform the storage operation. Forexample, as described herein, a storage operation priority, storagepreference, criteria, or other basis may be used to select a replicationcopy or first secondary copy to perform a storage operation. In oneexample, a first storage operation may be performed using a firstsecondary copy, step 440, if a selection criteria indicates that a firstsecondary copy should be used. For example, a criteria that a storageoperation is a high priority storage operation, or concurrent storageoperation scheduling, or other criteria, may cause a storage manager toselect a first secondary copy to be used for a particular storageoperation. In another example, a second storage operation having amedium priority which can use a replication copy may be performed usinga replication copy, step 450.

In both scenarios, information about the completed storage operation maybe stored to an index, step 455. Although a replication copy may havebeen used to create a secondary copy, the index may be updated with dataindicating that a primary copy or a first secondary copy was used tocreate a secondary copy. Such an index entry is useful in the event thatother components or modules may not recognize that a replication copy asan appropriate data source for creating a secondary copy, which maycause an error or other system failure.

Systems and modules described herein may comprise software, firmware,hardware, or any combination(s) of software, firmware, or hardwaresuitable for the purposes described herein. Software and other modulesmay reside on servers, workstations, personal computers, computerizedtablets, PDAs, and other devices suitable for the purposes describedherein. Software and other modules may be accessible via local memory,via a network, via a browser or other application in an ASP context, orvia other means suitable for the purposes described herein. Datastructures described herein may comprise computer files, variables,programming arrays, programming structures, or any electronicinformation storage schemes or methods, or any combinations thereof,suitable for the purposes described herein. User interface elementsdescribed herein may comprise elements from graphical user interfaces,command line interfaces, and other interfaces suitable for the purposesdescribed herein. Screenshots presented and described herein can bedisplayed differently as known in the art to input, access, change,manipulate, modify, alter, and work with information.

While the invention has been described and illustrated in connectionwith preferred embodiments, many variations and modifications as will beevident to those skilled in this art may be made without departing fromthe spirit and scope of the invention, and the invention is thus not tobe limited to the precise details of methodology or construction setforth above as such variations and modification are intended to beincluded within the scope of the invention.

What is claimed is:
 1. A method for performing a storage operation usinga replication copy, the method comprising: receiving from a managementmodule executing on computer hardware comprising at least one computerprocessor, an instruction to perform a storage operation on a first setof data stored on a first storage volume; receiving a storage policyindicating that the storage operation should be performed, on the firstset of data stored on the first storage volume; determining that areplication copy is available on a second storage volume, wherein thereplication copy is comprises a second set of data that is a copy of thefirst set of data; calculating a priority metric based on at least apriority associated with the storage operation; and performing thestorage operation on the second set of data associated with thereplication copy on the second storage volume rather than the first setof data on the first storage volume, based on the availability of thereplication copy and based on the priority metric wherein the storageoperation on the second set of data in the replication copy creates athird set of data that is a copy of at least a portion of the first andsecond sets of data.
 2. The method of claim 1, additionally comprisingupdating an index to indicate completion of the storage operation. 3.The method of claim 2, wherein said updating comprises modifying theindex to indicate that the storage operation was performed on the firstset of data after the storage operation was performed on the replicationcopy.
 4. The method of claim 1, additionally comprising generating thefirst set of data by creating a copy of a set of production data of aparticular software application.
 5. The method of claim 4, additionallycomprising additionally comprising monitoring changes to the productiondata with a filter driver.
 6. The method of claim 5, wherein saidgenerating the first set of data comprises processing a log filecontaining a least a portion of the changes monitored by the filterdriver.
 7. The method of claim 1, additionally comprising generating thereplication copy via a snapshot operation.
 8. The method of claim 1,additionally comprising generating the replication copy via a mirroringoperation.
 9. The method of claim 1, additionally comprising performinga second storage operation on the first set of data, wherein the secondstorage operation at least partially overlaps the first storageoperation.
 10. The method of claim 1, wherein said determining furthercomprises determining if the replication is online or offline.
 11. Astorage management system for performing a storage operation, the systemcomprising: a media agent component executing on computer hardwarecomprising at least one computer processor, the media agent componentconfigured to access a first copy of production data stored in a firststorage volume and a second copy of the production data stored in asecond storage volume; a storage management component communicativelycoupled to the media agent component and configured to, receive astorage operation request relating to the first copy of the productiondata, and determine that a the second copy of the production data isavailable on a second storage volume, wherein the replication copy iscomprises a second set of data that is a copy of the first set of data;calculate a priority metric based on at least a priority associated withthe storage operation; and wherein the media agent component is furtherconfigured to perform the storage operation using the second set of dataassociated with the second copy on the second storage volume rather thanthe first copy on the first storage volume based on the availability ofthe second volume and based on the priority metric wherein the storageoperation on the second set of data in the replication copy creates athird set of data that is a copy of both the first and second sets ofdata.
 12. The system of claim 11, wherein the storage managementcomponent is configured to instruct the media agent component to performthe storage operation.
 13. The system of claim 11, wherein the storagemanagement component is further configured to compare the prioritymetric with a predetermined threshold.
 14. The system of claim 11,further comprising a replication agent configured to generate the secondcopy of the production data based on the first copy of the productiondata.
 15. The system of claim 11, wherein the storage managementcomponent is configured to access a database to identify the second copyof the production data in response to said receiving the storageoperation request relating to the first copy of the production data. 16.The system of claim 11, wherein the media agent is configured to accessa storage operation schedule to determine the availability of the secondcopy of the production data.
 17. The system of claim 11, wherein themedia agent is configured to access at least one of the first and secondsets of data via a small computer system interface (SCSI) communicationslink.
 18. The system of claim 11, wherein the first storage volumecomprises a faster access time than the second storage volume.